Document release actions in audit logs - #3443
Conversation
Add release events (create, update, delete, trigger, entry add/change/remove, settings update) to the audit-logs event table, and add a dedicated section to the releases page explaining what is recorded and how to view it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pwizla
left a comment
There was a problem hiding this comment.
LGTM, mergeable when ready 🚀
The Drafter prompt already forbade em dashes and PR #3443 carried one anyway: the rule sits 300 lines before the first sentence is written, so it now runs again as a sweep at output time. Micro-edits had no rule at all, since that path loads router.md only and router.md never mentioned em dashes.
…#3444) * Add an em dash check to the auto-merge eligibility criteria Em dashes are not used in Strapi documentation and are a strong tell of unedited AI-generated prose. The self-healing workflow now lints them out before committing, and this check is the net under that: it reports, it never edits the PR. * Run style-lint before committing in the self-healing workflow The Style Checker prompt already forbids em dashes, but a prompt is a probabilistic filter and style-lint.sh is not: an em dash still reached PR #3443. Micro-edits skip the Style Checker entirely, so the script is their only style guard. The Router block is reordered first, since its git reset ran after the file edits and would have destroyed them. * Rewrite the self-healing PR descriptions to follow git-rules.md The canned body named no change, put the source PR as a bare URL instead of a Documents link, carried no preview link, and repeated boilerplate the label, assignee and draft status already convey. Both prompts now build the description from the actual diff. Also repairs the broken line continuations in the Drafter gh pr create call, which would have dropped the body, labels and draft flag. * Never let the style-lint pass stop the self-healing workflow from opening a PR A remaining em dash costs a few seconds of editing at review time. An abandoned PR costs re-reading the strapi/strapi diff and writing the page by hand, and the source PR does not come back: the next run only lists PRs merged in the last 24 hours, so anything skipped is silently lost. * State the em dash rule where the agent actually reads it The Drafter prompt already forbade em dashes and PR #3443 carried one anyway: the rule sits 300 lines before the first sentence is written, so it now runs again as a sweep at output time. Micro-edits had no rule at all, since that path loads router.md only and router.md never mentioned em dashes.
|
@gonbaum The self-healing system created this docs PR to document the strapi/strapi PR you created. |
pwizla
left a comment
There was a problem hiding this comment.
Approved from a tech. writing POV ✅
|
Merging it to ensure it's included in the next release. If something is wrong, please tell me and I'll fix it afterwards, @gonbaum |
This PR updates documentation based on strapi/strapi#27436.
Generated automatically by the docs self-healing workflow.
Review before merging.